SUPPORT / SAMPLES & SAS NOTES
 

Support

Usage Note 37753: Unpacking SAS® Content Server EAR files in order to change logging parameters

DetailsAboutRate It

At times, you might need to change the type of messages that the SAS Content Server writes to its log file. For example, you might want to changes the message type from INFO to DEBUG. To make this type of change, you must unpack the SAS Content Server EAR file.

The following instructions explains how to unpack manually the SAS Content Server EAR file:

  1. Copy SAS_configuration_diretory\Lev1\Web\Staging\sas.wip.scs9.2.ear to a temporary directory such as C:\tmp in a Windows operating environment or /tmp in a UNIX operating environment.
  2. From that directory, submit the following command:
  3. JDK_1.5.x_home_directory\bin\jar -xvf sas.wip.scs9.2.ear
  4. After the EAR file's contents have been extracted, copy the file sas.svcs.scs.war to a second temporary directory such as c:\tmp2 (under Windows) or /tmp2 (under UNIX).
  5. From that second temporary directory, submit the following command:
  6. JDK_1.5.x_home_directory\bin\jar -xvf sas.svcs.scs.war
  7. Once the WAR files contents are extracted, edit the following file:
  8. second_temporary_directory\WEB-INF\web.xml
  9. Change the <param–value> to point to a directory on the file system, as shown in the following directory:
    <param–value>SAS_configuration_directory\Lev1\Web\Applications\SASContentServer\log4j.xml</param–value>
  10. Copy both the log4j.xml and the log4j.dtd files into the directory that is specified in the previous step.
  11. SAS_configuration_directory\Lev1\Web\Applications\SASContentServer\log4j.xml
    SAS_configuration_directory\Lev1\Web\Applications\SASContentServer\log4j.dtd
  12. From that second temporary directory, submit the following command:
  13. JDK_1.5.x_home_directory\bin\jar -cvf sas.svcs.scs.war *
  14. Once the files have been compressed into a new WAR file, copy the sas.svcs.scs.war file from the second temporary directory to the first temporary directory, replacing the original file.
  15. From that first temporary directory, submit the following command:
  16. JDK_1.5.x_home_directory\bin\jar -cvf sas.wip.scs9.2.ear *
  17. Once the files have been compressed into a new EAR file, copy the sas.wip.scs9.2.ear file to a following directory, replacing the existing file:
    <SAS_Config_Dir>\Lev1\Web\Staging.
  18. Deploy the newly created sas.wip.scs9.2.ear file. For instructions on deploying the EAR file, consult the SAS® 9.2 Intelligence Platform: Web Application Administration Guide.


Operating System and Release Information

Product FamilyProductSystemProduct ReleaseSAS Release
ReportedFixed*ReportedFixed*
SAS SystemSAS Enterprise BI ServerMicrosoft Windows Server 2003 Datacenter Edition4.29.39.2 TS2M09.3 TS1M0
Microsoft Windows Server 2003 Enterprise Edition4.29.39.2 TS2M09.3 TS1M0
Microsoft Windows Server 2003 Standard Edition4.29.39.2 TS2M09.3 TS1M0
Microsoft Windows XP Professional4.29.39.2 TS2M09.3 TS1M0
Windows Vista4.29.39.2 TS2M09.3 TS1M0
64-bit Enabled AIX4.29.39.2 TS2M09.3 TS1M0
64-bit Enabled HP-UX4.29.39.2 TS2M09.3 TS1M0
64-bit Enabled Solaris4.29.39.2 TS2M09.3 TS1M0
HP-UX IPF4.29.39.2 TS2M09.3 TS1M0
Linux4.29.39.2 TS2M09.3 TS1M0
Linux for x644.29.39.2 TS2M09.3 TS1M0
Solaris for x644.29.39.2 TS2M09.3 TS1M0
Microsoft Windows XP 64-bit Edition4.29.39.2 TS2M09.3 TS1M0
Microsoft® Windows® for x644.29.39.2 TS2M09.3 TS1M0
Microsoft Windows Server 2003 Enterprise 64-bit Edition4.29.39.2 TS2M09.3 TS1M0
Microsoft Windows Server 2003 Datacenter 64-bit Edition4.29.39.2 TS2M09.3 TS1M0
z/OS4.29.39.2 TS2M09.3 TS1M0
Microsoft® Windows® for 64-Bit Itanium-based Systems4.29.39.2 TS2M09.3 TS1M0
* For software releases that are not yet generally available, the Fixed Release is the software release in which the problem is planned to be fixed.